Providing search results based on execution of applications

ABSTRACT

A method includes displaying a first graphical user interface (GUI) via a first native application installed on a mobile computing device. The first GUI is configured to accept a search query, including one or more search terms, and transmit the search query to a search engine. The method includes receiving search results including a post execution view of a second native application for display on the touchscreen. The post execution view is a second GUI providing access to a function associated with the second native application. The method includes, at the search engine, identifying, based on the search terms of the search query, the second native application in an index that stores information and code related to native applications. The method includes executing code associated with the second native application to generate a post execution view. The method includes transmitting the post execution view to the mobile computing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/195,709, filed on Mar. 3, 2014 and U.S. patent applicationSer. No. 14/195,643, filed on Mar. 3, 2014, which claim the benefit ofU.S. Provisional Application No. 61/924,032, filed on Jan. 6, 2014 andU.S. Provisional Application No. 61/771,614, filed on Mar. 1, 2013. Theentire disclosures of the applications referenced above are incorporatedby reference.

FIELD

This disclosure relates to the field of search in computingenvironments. In particular, this disclosure relates to generatingsearch results containing state links to applications.

BACKGROUND

The World Wide Web (the “Web”) contains endless information and itcontinues to experience an explosive growth of information. Users accessthe information via web browsers which allow the users to view web pagescontaining the information. Due to the increasing number of webpages,web search engines became available to aid users in finding specificinformation. Most search engines perform three main functions: crawling,indexing, and searching. A web crawler is an automated web browser usedto retrieve information from web pages. Once the web crawler collectsthe information on each web page, the information is then indexed in thesearch engine database. Indexing parses and stores the informationgathered by the web crawler to expedite the retrieval of information.The searching process is initiated when a user enters a search queryinto the search engine. The search engine references its index andprovides the results of the best matched web pages according to theprovided query.

SUMMARY

One aspect of the disclosure provides a method for generating searchresults containing state links to applications. The method includesreceiving a search query from a remote computing device, generating astate link to a state of a native application based on the search queryand providing the state link to the remote computing device, all by aprocessing device. In some implementations, the state link is providedto the remote computing device with one or more other state links tothird party applications. In some implementations, the nativeapplication is a third party native application. The native applicationcan correspond to a third party application having one or more versions.The state link can include an application resource identifiercorresponding to the native application and is used to access the statein the native application version of the third party application.

Implementations of the disclosure may include one or more of thefollowing features. In some implementations, the state link furtherincludes a web resource identifier being used to access a webapplication corresponding to the third party application at the samestate of the third party application. The state link may include one ormore other application resource identifiers.

In some examples, determining the state link includes determining anapplication resource identifier based on the search query and embeddingthe application resource identifier into the state link. Additionally oralternatively, the native application may correspond to a third partyapplication. The third party application has one or more versionsincluding the native application. Determining the application resourceidentifier may include generating a request to a server associated withthe third party application based on the search query, receiving aresponse from the server associated with the third party application andgenerating the application resource identifier based on the response.The response may include a web resource identifier to access a webapplication version of the third party application at the state.Generating the application resource identifier may include convertingthe web resource identifier to the application resource identifier usinga conversion rule.

In some implementations, determining the application resource identifierincludes identifying a command template corresponding to the nativeapplication and generating the application resource identifier based onthe command template and the search query. The command templateindicates the native application and includes one or more parameterfields that receive state parameters.

Another aspect of the disclosure provides a search server. The searchserver includes a network interface device and a processing device. Theprocessing device executes computer readable instructions. When theinstructions are executed by the processing device, the instructionscause the processing device to receive a search query from a remotecomputing device via the network interface device, generate a state linkto a state of a native application based on the search query and providethe state link to the native application to the remote computing device.The state link may be provided to the remote computing device with oneor more other state links to the third party application. The nativeapplication is a third party native application. The native applicationcorresponds to a third party application having one or more versions.The state link includes an application resource identifier correspondingto the native application and is used to access the state in the nativeapplication version of the third party application. The state linkfurther includes a web resource identifier being used to access a webapplication corresponding to the third party application at the samestate of the third party application. The state link includes one ormore other application resource identifiers.

In some implementations, the computer readable instructions cause theprocessing device to determine the state link by determining anapplication resource identifier based on the search query and embeddingthe application resource identifier into the state link. The nativeapplication can correspond to a third party application. The third partyapplication can have one or more versions including the nativeapplication. In some implementations, the computer readable instructionscause the processing device to determine the application resourceidentifier by generating a request to a server associated with the thirdparty application based on the search query, receiving a response fromthe server associated with the third party application, and generatingthe application resource identifier based on the response.

In some examples, the response includes a web resource identifier toaccess a web application version of the third party application at thestate. In some implementations, the computer readable instructions causethe processing device to generate the application resource identifier byconverting the web resource identifier to the application resourceidentifier using a conversion rule. The computer readable instructionscause the processing device to determine the application resourceidentifier by identifying a command template corresponding to the nativeapplication and generating the application resource identifier based onthe command template and the search query. The command templateindicates the native application and includes one or more parameterfields that receive state parameters.

Another aspect of the disclosure provides a method for generating searchresults containing state links to applications. The method includesreceiving a query containing one or more query parameters from a remotecomputing device and identifying a set of third party applicationscorresponding to the one or more query parameters, all by a processingdevice. For each third party application, the method includestransmitting at least a subset of the one or more query parameters to aserver associated with the third party application, receiving a responsefrom the server associated with the third party application, andgenerating a state link to a native application version of the thirdparty application based on the response. The method further includesproviding the states links to the remote computing device. The one ormore query parameters include a search query including one or more queryterms. The one or more query parameters further include one or more of ageolocation of the remote computing device, an operating system of theremote computing device, or an identifier of a user of the remotecomputing device.

In some examples, the state link provides access to a state of a nativeapplication version of the third party application. In someimplementations, the state link includes a screen shot indicative of thestate. In some implementations, the state link includes an applicationresource identifier indicating a reference to the native applicationversion and one or more state parameters corresponding to the state. Theone or more state parameters can be used by the native application toaccess the state. Additionally or alternatively, the state link mayinclude a web resource identifier indicating a domain name of a webserver associated with the third party application and the one or morestate parameters. The web server hosts a web application version of thethird party application.

In some examples, transmitting the query parameters includestransmitting at least a subset of the one or more query parameters to aweb server that hosts a web application that is a web applicationversion of the third party application. Transmitting the queryparameters may further include selecting a command templatecorresponding to the third party application from a plurality of commandtemplates, formatting an outgoing request based on the command templateand at least a subset of the one or more query parameters andtransmitting the outgoing request to the web server.

In some implementations, receiving the response includes receiving a webresource identifier indicating a domain name of a web server associatedwith the third party application and one or more state parameterscorresponding to a state of the web application that are used by the webapplication to access the state. Determining the state link to thenative application includes converting the web resource identifier to anapplication resource identifier indicating a reference to the nativeapplication version of the third party application and the one or morestate parameters. The remote computing device is configured to use theapplication resource identifier to launch the native application to thestate indicated by the one or more state parameters. The remotecomputing device is configured to receive the state link and to attemptto access the state on the native application version using theapplication resource identifier before attempting to access the webapplication version using the web resource identifier.

Yet another aspect of the disclosure provides a search server forgenerating search results containing state links to applications. Thesearch server includes a network interface device and a processingdevice. The processing device executes computer readable instructions,that when executed by the processing device, cause the processing deviceto receive a query containing one or more query parameters from a remotedevice and identify a set of third party applications corresponding tothe one or more query parameters. For each third party application, theprocessing device transmits at least a subset of the one or more queryparameters to a server associated with the third party application,receives a response from the server associated with the third partyapplication, and generates a state link to a native application versionof the third party application based on the response. The processingdevice provides the state links to the remote computing device. The oneor more query parameters include a search query including one or morequery terms. The one or more query parameters can further include one ormore of a geolocation of the remote computing device, an operatingsystem of the remote computing device, or an identifier of a user of theremote computing device.

In some implementations, the state link provides access to a state of anative application version of the third party application and providesthe state link to the remote computing device. In some implementations,the state link includes an application resource identifier indicating areference to the native application version and one or more stateparameters corresponding to the state. The one or more state parametersare can be used by the native application to access the state.Additionally or alternatively, the state link may further include a webresource identifier indicating a domain name of a web server associatedwith the third party application and the one or more state parameters.The web server hosts a web application version of the third partyapplication. The computer readable instructions cause the processingdevice to transmit the query parameters by transmitting at least asubset of the one or more query parameters to a web server that hosts aweb application that is a web application version of the third partyapplication. In some implementations, the state link includes a screenshot indicative of the state.

In some examples, the computer readable instructions further cause theprocessing device to transmit the query parameters by selecting acommand template corresponding to the third party application from aplurality of command templates, formatting an outgoing request based onthe command template and at least a subset of the one or more queryparameters and transmitting the outgoing request to the web server.Additionally or alternatively, the computer readable instructions maycause the processing device to receive the response by receiving a webresource identifier indicating a domain name of a web server associatedwith the third party application and the one or more state parameterscorresponding to a state of the web application that are used by the webapplication to access the state.

In some implementations, the computer readable instructions further casethe processing device to determine the state link to the nativeapplication by converting the web resource identifier to an applicationresource identifier indicating a reference to the native applicationversion of the third party application and the one or more stateparameters. The remote computing device is configured to use theapplication resource identifier to launch the native application to thestate indicated by the one or more state parameters. In some scenarios,the remote computing device may be configured to receive the state linkand to attempt to access the state on the native application versionusing the application resource identifier before attempting to accessthe web application version using the web resource identifier.

Yet another aspect of the disclosure provides a method for generatingsearch results containing state links to applications. The methodincludes receiving a query containing one or more query parameters froma remote computing device and identifying a set of third partyapplications corresponding to the one or more query parameters. For eachthird party application, the method includes selecting a commandtemplate corresponding to the third party application from a pluralityof command templates, generating a resource identifier corresponding tothe third party application based on the command template and at least asubset of the one or more query parameters, and generating a state linkbased on the resource identifier. The method further includes providingthe state links to the remote computing device, all by the processingdevice. The one or more query parameters include a search queryincluding one or more query terms, and may include one or more of ageolocation, an operating system, or an identifier of the remotecomputing device. The command template is selected based on afunctionality implicated in the query, and may be formatted to leveragea specific functionality of the third party application.

The remote computing device can be configured to access the third partyapplication using the state link. In some examples, the resourceidentifier is a web resource identifier indicating a domain name of aweb server that hosts a web application version of the third partyapplication. The web resource identifier can include one or more stateparameters corresponding to the at least the subset of the queryparameters. In some implementations, the web resource identifier may bea uniform resource locator. The resource identifier may be anapplication resource identifier indicating a native application versionof the third party application. The application resource identifier canfurther include one or more state parameters corresponding to the atleast the subset of the query parameters.

In some implementations, the state link includes at least oneapplication resource identifier and at least one web resourceidentifier. The remote computing device can be configured to receive thestate link and to attempt to access the state on the native applicationversion using the application resource identifier before attempting toaccess the web application version using the web resource identifier. Insome implementations, the state link includes a screen shot indicativeof the state.

Yet another aspect of the disclosure provides a search server forgenerating search results containing state links to applications. Thesearch server includes a network interface device and a processingdevice that executes computer readable instructions. When theinstructions are executed, the processing device receives a querycontaining one or more query parameters from a remote computing deviceand identifies a set of third party application corresponding to the oneor more query parameters. For each third party application, theprocessing device selects a command template corresponding to the thirdparty application from a plurality of command templates, generates aresource identifier corresponding to the third party application basedon the command template and at least a subset of the one or more queryparameters, and generates a state link based on the resource identifier.The processing device provides the state links to the remote computingdevice. The command template can be selected based on a functionalityimplicated in the query and may be formatted to leverage a specificfunctionality of the third party application. The remote computingdevice can be configured to access the third party application using thestate link.

In some scenarios, the resource identifier is a web resource identifierindicating a domain name of a web server that hosts a web applicationversion of the third party application. The web resource identifier canfurther include one or more state parameters corresponding to the atleast the subset of the query parameters.

In some scenarios, the resource identifier is an application resourceidentifier indicating a native application version of the third partyapplication. The application resource identifier can further include oneor more state parameters corresponding to the at least the subset of thequery parameters.

In some implementations, the state link may include at least oneapplication resource identifier and at least one web resourceidentifier. The remote computing device is configured to receive thestate link and to attempt to access the state on the native applicationversion using the application resource identifier before attempting toaccess the web application version using the web resource identifier.The state link may include a screen shot indicative of the state.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B illustrate an example system for performing searches.

FIG. 2 illustrates an example set of components of the remote computingdevice.

FIG. 3 illustrates an example set of components of the search server.

FIGS. 4A and 4B illustrate example sets of operations for a method fortransmitting query parameters to servers associated with one or morethird party applications.

FIG. 5 illustrates an example set of operations for a method forprocessing a query from a remote computing device.

FIG. 6 illustrates an example set of operations for a method forprocessing a query from a remote computing device.

FIGS. 7A-10 illustrate various examples of searches that can beperformed on a remote computing device.

FIGS. 11A and 11B illustrate an example set of operations for a methodfor processing a query.

FIGS. 12A and 12B illustrate an example set of operations for a methodfor processing a query.

FIG. 13 illustrates one embodiment of components of an example machineable to read instructions from a machine-readable medium and executethem in a processor (or controller).

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

The Figures and the following description relate to preferredembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesof what is claimed.

Reference will now be made in detail to several embodiments, examples ofwhich are illustrated in the accompanying figures. It is noted that,wherever practicable, similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments of the disclosed system (or method) for purposes ofillustration only. One skilled in the art will readily recognize fromthe following description that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles described herein.

FIGS. 1A and 1B illustrate an example system 10 for performing searches.The system 10 includes a search server 300 in communication with one ormore remote computing devices 200 via a network 110. The remotecomputing devices 200 can refer to, for example, a mobile computingdevice (e.g., a smartphone 200 a or a tablet computer 200 b), astationary computing device 200 c (e.g., a desktop computer or laptopdevice), wearable computers, video game consoles, smart appliances,and/or any other suitable device that includes a user interface and anetwork interface device. The search server 300 can also communicatewith application servers 120 and web servers 130 via the network 110.The search server 300 and the remote computing devices 200 are furtherdescribed below. The term “server” may refer to computing devices thatprimarily serve client devices, such as remote computing devices 200 orother servers. Furthermore, while FIGS. 1A and 1B depict a standaloneserver, the search server 300 may be a collection of devices at one ormore data centers. These devices may work independently or in adistributed manner. Although FIGS. 1A and 1B illustrate one of eachrespective device type, the system 10 can include any number and/orcombination of devices.

In operation, a remote computing device 200 can execute, at least inpart, a search application 214 that displays a graphical user interface(GUI) 250 that allows a user to enter search queries 262. A search query262 is a query parameter that the remote computing device 200 providesto the search server 300, which the search server 300 uses to determinesearch results 360. For example, the user may enter a search query 262into a search bar 252 (e.g., a search box) of the GUI 250 using atouchscreen keypad, a mechanical keypad, and/or via speech recognition.A search query 262 may include one or more query terms. A query term mayrefer to a word, number, and/or symbol in the search query 262. The usercan interact with the GUI 250 of the search application 214 to transmitthe search query 262 to the search server 300. For example, with respectto FIG. 1B, a user can enter the search query 262 (i.e., “Late NightDiners”) and select (e.g., touch or click) a search button 254 of theGUI 250 in order to transmit the search query 262 to the search server300.

In some examples, the remote computing device 200 (e.g., the searchapplication 214) may transmit additional query parameters 264 to thesearch server 300 along with the search query 262. The additional queryparameters 264 can include, for example, platform data (e.g., devicetype, operating system version, web-browser version, a list of nativeapplication installed on the remote computing device 200), geo-locationdata (e.g., the location of the remote computing device 200), anidentity of a user of the remote computing device 200 (e.g., ausername), user preferences (e.g., user's language preference, user'slocation preferences, whether the user prefers free applications or payapplications, user's browsing history) partner specific data, and/orother suitable data. In some implementations, the search application 214can bundle the search query 262 and the additional query parameters 264into a query wrapper 260. A query wrapper 260 can contain the queryparameters 262, 264 in a format defined by a schema implemented by thesearch server 300. In some implementations, one or more of theadditional query parameters 264 may be stored on a cache of the searchserver 300, such that the additional query parameter 264 can be lookedup upon receipt of the query wrapper 260. The search server 300 can useone or more of the query parameters 262, 264 included in the querywrapper 260 to generate the search results 360.

The search application 214 may be implemented as a client webapplication (e.g., a web browser), a native application, and/or a partof the operating system. A “native application” is an application thatis executed, at least in part, by the processing device of a remotecomputing device 200. A “web application” is an application that isexecuted, at least in part, by a web server 130 and accessed by a remotecomputing device 200 via a web browser of the remote computing device200. In some examples, a search application 214 is an application thatthe party associated or affiliated with the search server 300 developsto provide remote user computing devices 200 access to the searchcapabilities of the search server 300.

In some implementations, the search application 214 is configured tocommunicate with a partner device 140. The partner device 140 receivesquery parameters 262, 264 from a remote computing device 200, which thepartner device 140 provides to the search server 300. The search server300 provides the search results 360 to the partner device 140. Thepartner device 140 can communicate the search results 360 to the remotecomputing device 200. The partner device 140 may further process thesearch results 360 or add content to the search results 360 (e.g.,advertisements, visual indicators, and/or additional result objects362).

The search server 300 receives the search query 262 and/or the otherquery parameters 264 and determines a set of search results 360corresponding to the search query 262 and/or the other query parameters264. The search results 360 can include one or more result objects 362.A result object 362 can refer to data that is provided to the remotecomputing device 200 that can be displayed by the remote computingdevice 200. A result object 362 corresponding to a third partyapplication can include one or more state links 364 to a state of thethird party application, one or more visual indicators 366 correspondingto the third party application (e.g., an icon of the third partyapplication, a logo or image of an entity corresponding to the state ofthe third party application, and/or a screen shot of the third partyapplication), and other data 368 corresponding to the third partyapplication (e.g., rankings, ratings, and/or descriptions correspondingto the third party application and/or the entity corresponding to thestate of the third party application).

A state link 364 can refer to an object that includes text and/or imagesthat a user may select (e.g., touch) via a user interface of the remotecomputing device 200. The remote computer device 200 displays the statelink 364 and in some implementations, renders the state link 364. Eachuser selectable state link 364 may include one or more resourceidentifiers 365 for accessing a specific state of a third partyapplication. A resource identifier 365 is a string of letters, numbers,and/or characters that can reference a particular state of the thirdparty application. Types of resource identifiers include web resourceidentifiers 365 a and application resource identifiers 365 b. Webresource identifiers 365 a (e.g., URLs) can be used to access states ofweb applications. A web resource identifier 365 a can include areference to a domain of a web server 130 that serves the webapplication and one or more state parameters that the web server 130uses to access a particular state of the application. Applicationresource identifiers 365 b can be used to access states of nativeapplications. An application resource identifier 365 b can include areference to a native application to be launched by the remote computingdevice 200 and one or more state parameters that can be used by theremote computing device 200 to access a particular state of theapplication.

A state link 364 can include one or more application resourceidentifiers 365 b and a web resource identifier 365 a, such that when auser selects a state link 364, the remote computing device 200 canlaunch a native application to a state referenced in the applicationresource identifier 365 b and/or access a web application at a stateindicated by the web resource identifier 365 a. The text and/or imagesof a state link 364 displayed to a user may indicate the state of theapplication that will be accessed in response to selection of the statelink 364. For example, if the state link 364 is to a song in a musicplaying application, the text and/or images may identify the song thatwill be played by the music playing application when the user selectsthe state link 364.

In the example of FIG. 1B, the user has entered the search query “LateNight Diners.” In response to the search query 262 and possibly one ormore additional parameters 264 (e.g., geo-location of the remotecomputing device 200, operating system type, username, list of nativeapplications installed on the remote computing device, and/or languagepreferences of the user), the search server 300 returns search results360 that include a first result object 362 a corresponding to the YELP®application. The YELP® application is an application that providescrowd-sourced reviews and ratings of various establishments as well asinformation specific to the establishments (e.g., hours of operation,contact information, and location). Each establishment may have an entrywithin the application, whereby users can view the ratings, reviews, andany other information regarding the establishment by searching for theestablishment or by location. The result object 362 a includes statelinks 364 to three different states of the YELP® native application. Thestate links 364 include a first state link 364 a to a statecorresponding to a first entry for an INTERNATIONAL HOUSE OF PANCAKES®restaurant or IHOP®, a second state link 364 b to the statecorresponding to a second entry for a DENNY'S® restaurant, and a thirdstate link 364 c to a state corresponding to a third entry for a TACOBELL® restaurant. Each state link 364 can include one or more resourceidentifiers 365 that allow the remote computing device 200 to access theYELP® application at a state indicated by the one or more resourceidentifiers 365. For example, the state link 364 a corresponding toIHOP® can include one or more application resource identifiers 365 b,whereby each application resource identifier 365 b corresponds to adifferent native application version of the YELP® application (e.g., aniOS version and an ANDROID® version), but correspond to the same state(e.g., an entry for the IHOP® restaurant). The state link 364 a can alsoinclude a web resource identifier 365 a that corresponds to a webapplication version of the YELP® application and corresponds to the samestate (e.g., the entry for the IHOP® restaurant).

The user can select (e.g., press or touch) one of the state links 364,and in response to the selection, the remote computing device 200 canaccess the state indicated by resource identifiers 365 embedded in thestate link 364. In some scenarios, the remote computing device 200 canlaunch a native application indicated by an application resourceidentifier 365 b embedded in the state link 364 at the state indicatedby the application resource identifier 365 b. For example, if the userselects the first state link 364 a, the remote computing device 200 canattempt to launch the YELP® native application and access an entry foran IHOP® indicated by the state link (e.g., an entry for an IHOP®restaurant located near the geo-location of the remote computing device200) using an application resource identifier 365 b embedded in thestate link 364 a. If the remote computing device 200 is unable to launchthe YELP® native application (e.g., the native application is notinstalled on the remote computing device 200), the remote computingdevice 200 can access the YELP® web application via a web browserapplication of the remote computing device 200 using the web resourceidentifier 365 a embedded in the state link 364 a. The search results360 of FIG. 1B and the manner by which the search results 360 aredisplayed are provided for example only.

In operation, the search server 300 receives the search query 262 and/orthe query parameters 264 and identifies one or more third partyapplications that are relevant to the search query 262 and/or the queryparameters 264. The search server 300 generates resource identifiers 365to specific states of the third party applications which are likelyrelevant to the search query 262 and/or the query parameters 264. Thestate links 364 included in a result object 362 are based on theresource identifiers 365 that are generated by the search server 300.

A third party application can refer to an application developed by aparty that is unaffiliated with the search server 300. In someimplementations, the third party application can include one or morenative applications and one or more web applications which all providethe same or similar functionality. For example, a third partyapplication for a music player that allows users to share playlists andsong recommendations may include a “pay” version of the nativeapplication for the APPLE® iOS operating system, a “free” version of thenative application for the APPLE® iOS operating system, a “pay” versionof the native application for the ANDROID® operating system, and a“free” version of the native application for the ANDROID® operatingsystem. The third party application may also include a mobile webapplication and a full-version web application that can be accessed by aweb browser on a mobile remote computing device 200 a and/or a desktopremote computing device 200 c. All of the different versions may haveoverlapping functions and may be classified under the third partyapplication.

The search server 300 can parse and process the query wrapper 260 toidentify third party applications that are relevant to the queryparameters 262, 264. As discussed herein, the search query 262 mayinclude query terms that identify or otherwise implicate a name of athird party application, a desired functionality, or an entity. Thesearch server 300 can perform one or more types of searches to determinea set of third party applications based on the query parameters 262,264. For example, if the search server 300 receives the query “make areservation at French Laundry at 7:00 PM,” the search server 300 canidentify that “French Laundry” has an entity type of restaurant andprocess the rest of the query terms to determine that the user desiresfunctionality that allows the user to make reservations. The searchserver 300 can then identify a set of third party applications that canbe utilized to make restaurant reservations.

In some implementations, the search server 300 is configured to forwardone or more of the query parameters 262, 264 to a server associated withthe third party application. More specifically, the search server 300can transmit the one or more of the query parameters 262, 264 to aserver associated with the third party application to leverage aspecific functionality of the third party application. A functionalityof a third party application can refer to a particular task that thethird party application is configured to perform or particularinformation that the third party application is configured to provide.For example, a functionality of a third party application may be toprovide geo-coordinates on a map, to search for a particular song in amusic library of a third party application, to find the price of, andbook, an airline ticket to a destination from a source location, or tosearch for reviews of near-by restaurants. Thus, if the third partyapplication is a review application that is centered around a searchingplatform (e.g., the third party application returns information andcrowd-sourced reviews for various establishments), the search server 300may provide one or more of the query parameters 262, 264 to a web server130 or application server 120 of the review application to receivereviews corresponding to the one or more query parameters 262, 264. Thesearch server 300 can forward the query parameters 262, 264 to leveragethe functionality of a third party application using a schemaimplemented by the third party to implicate the functionalities thereof.

Once the search server 300 has determined a set of third partyapplications that are relevant to the query 262, the search server 300can generate requests according to each third party application'sschema, which it can send to each respective third party application(e.g., a web server 130 or an application server 120). The third partyapplication can provide a response to the request to the search server300. The response can include the information indicating the requesteddata (e.g., one or more webpages showing search results), one or moreresource identifiers 365 indicating where the requested data can beaccessed, and/or one or more state parameters that respectively indicateone or more states of the third party application where the requesteddata can be accessed. In this way, the indicated state can be accessedat a later time without having to repeat the query. As used herein, thestate of a third party application can refer to a particular page orscreen of the third party application (e.g., a particular page of a webapplication or a particular screen of a native application). Further,the state of the third party application may be dependent on a set ofstate parameters. For instance, if a third party application displayssearch results for a particular set of query terms, the state of thethird party application is a function, at least in part, of the queryterms. Thus, a state of a web application can be referenced by a domainname of the web application and the state parameters that correspond tothe particular state. A state of a native application can be accessedusing the name of the third-party application and the state parameterscorresponding to the state.

In some implementations, the search server 300 is further configured toprovide a post execution view of a state of third party applications. Insome implementations, the post execution view is a screen shot of eithera native application or a web application at the state. The screen shotcan be provided with the state link 364 in the result object 362, suchthat a user can see the state of the third party application. In someimplementations, the post-execution view is a graphical user interface250 that is displayed to the user, such that the user can access thespecific functionality defined in the state.

FIG. 2 illustrates an example set of components of a remote computingdevice 200. The remote computing device 200 can include a processingdevice 210, a network interface 220, a storage device 230, and a userinterface device 240. The remote computing device 200 can includeadditional components not depicted in FIG. 2 (e.g., accelerometer,sensors, GPS module).

The processing device 210 includes memory (e.g., RAM and/or ROM) thatstores computer readable instructions and one or more processors thatexecute the computer readable instructions. In implementations where theprocessing device 210 includes more than one processor, the processorscan execute in a distributed or individual manner. The processing devicecan execute an operating system 212, a search application 214, a webbrowser application 216, and one or more other native applications 218.The operating system 212 acts as an interface between higher levelapplications 214, 216, 218 and the processing device 210.

The network interface 220 includes one or more devices that areconfigured to communicate with the network 110. The network interface220 can include one or more transceivers for performing wired orwireless communication. Examples of the network interface 220 caninclude, but are not limited to, a transceiver configured to performcellular communications (e.g., transmission using the third generation(3G) or fourth generation (4G) telecommunications standards), atransceiver configured to perform communications using the IEEE 802.11wireless standard, an Ethernet port, a wireless transmitter, and auniversal serial bus (USB) port.

The storage device 230 can include one or more computer readable mediumsthat store data. The storage device 230 can store some or all of thecomputer readable instructions that define the search application 214,the web browser application 216, and the one or more other nativeapplications 218. The storage device 230 can store other data as well(e.g., media contents, application data, contacts, documents).

The user interface device 240 can include one or more devices that allowa user to interact with the remote computing device 200. The userinterface device 240 can include one or more of, for example, atouchscreen, a QWERTY keyboard, a display device, speakers, a touchpad,and a microphone. The user interface device 240 receives input from theuser and provides the input to the processing device 210. The userinterface device 240 receives output from the processing device 210 andoutputs the output to the user.

The web browser application 216 is an application that requests web datafrom a web browser and displays the data on the user interface device240. The web browser application 216 can be used to access webapplications. In some implementations, the web browser application 216can access a specific state of a web application by accessing the webserver 130 located in the domain portion of a web resource identifier365 b and providing a request to the web server 130 using the stateparameters indicated in the path portion of the web resource identifier365 b. Web applications can provide any suitable functionality.

The native applications 218 are applications that are executed, in part,by the processing device 210. Native applications 218 can be developedby third parties and made available to consumers in a variety ofmanners. For instance, a user can download a native application to theremote computing device 200 from an application retail store (e.g., fromGOOGLE PLAY® developed by Google Inc., the APP STORE® developed by AppleInc.) or from a website associated with the third party. Additionally oralternatively, the user can load a native application into the storagedevice 230 of the remote computing device 200 from a removable media,such as a CD-ROM. Native applications 218 can provide any suitablefunctionality. Examples of native applications can include, but are notlimited to, word processing applications, messaging applications, mediastreaming applications, social networking applications, e-readerapplications, and games.

The search application 214 presents a graphical user interface 250 (GUI)that allows a user to enter a search query 262 and displays searchresults 360. In some implementations, the GUI 250 can display a searchbar 252 whereby the user can provide text and/or speech input into thesearch bar 252. Additionally, or alternatively, the operating system 212of the remote computing device 200 can display the search bar 252 on thehome screen of the remote computing device 200, whereby a user can enterthe search query 262 directly from the home screen. In theseimplementations, when the user enters the search query 262 into thesearch bar 252 displayed on the home screen and executes the search, theoperating system 212 of the remote computing device 200 can launch thesearch application 214.

When the user executes a search query 262 (e.g., by pressing the searchbutton 254), the search application 214 can generate a query wrapper 260that contains the search query 262 and any other query parameters 264.The search application 214 can obtain the other query parameters 264 inany suitable manner. For example, the search application 214 can obtaininformation regarding the device (e.g., device type, operating systemtype, operating system version) from a file in the storage device 230 orin the memory of the processing device 210. Additionally oralternatively, the search application 214 can obtain informationregarding the device from a sensor or component of the remote computingdevice 200 (e.g., the geo-location can be obtained from a GPS module ofthe remote computing device 200). The search application 214 can createa query wrapper 260 based on the provided search query 262 and theobtained query parameters 264.

The search application 214 transmits the query wrapper 260 to the searchserver 300, which responds with the search results 360. The searchapplication 214 displays the search results 360 in the GUI 250 of thesearch application 214. As previously discussed, the search application214 can display state links 364 to access resources that are relevant tothe query parameters 262, 264. The state links 364 can includeapplication resource identifiers 365 b that can be used to launch athird party application and access a specific state within the thirdparty application. When the user selects a state link 364, the searchapplication 214 can initiate the accessing of the third partyapplication at the specific state. In some implementations, the searchapplication 214 attempts to launch a native application 218 version of athird party application. To initiate launching the native application218 to the specific state, the search application 214 provides aninstruction to launch the third party application to the operatingsystem 212 using the information provided in the state link 364. Theoperating system 212 can attempt to launch a native application 218indicated by an application resource identifier 365 b in the state link364, and if unsuccessful, can attempt to access the third partyapplication via the web browser application 216 (i.e., leverage the webapplication version of the third party application).

FIG. 3 illustrates an example set of components of the search server300. The search server 300 can include a processing device 310, anetwork interface 320, and a storage device 330. The search server 300may include additional components not explicitly shown in FIG. 3. Thesearch server 300 can be implemented as a single device or a collectionof devices (e.g., rack mounted servers). The search server 300 may belocated at a single location (e.g., at a single data center) or atmultiple locations (e.g., multiple data centers).

The processing device 310 includes memory (e.g., RAM and/or ROM) thatstores computer readable instructions and one or more processors thatexecute the computer readable instructions. In implementations where theprocessing device 310 includes more than one processor, the processorscan execute in a distributed or individual manner. The processing devicecan execute one or more of a search module 312, a forwarding module 314,a linking module 316, a viewing module 318 and a results module 319. Theprocessing device 310 may further execute an operating system (notshown) that acts as an interface between the one or more modules 312,314, 316, 318, 319 and the processing device 310.

The network interface 320 includes one or more devices that can performwired and/or wireless (e.g., WiFi or cellular) communication. Examplesof the network interface device 320 include, but are not limited to, atransceiver configured to perform communications using the IEEE 802.11wireless standard, an Ethernet port, a wireless transmitter, and auniversal serial bus (USB) port.

The storage device 330 can include one or more computer readable mediumsthat store data. The storage device 330 can store some or all of thecomputer readable instructions and other suitable data. In someimplementations, the storage device stores one or more of an applicationdata store 332, an entity data store 334, and a command template datastore 336.

The application data store 332 may include one or more databases,indices (e.g., inverted indices), files, or other data structuresstoring this data. The application data store 332 includes applicationdata of different third party applications. The application data of anapplication may include one or more of keywords associated with theapplication, reviews associated with the application, the name of thedeveloper of the application, the platform of the application, the priceof the application, application statistics (e.g., a number of downloadsof the application and/or a number of ratings of the application), acategory of the application, and other information. The application datastore 332 may include metadata for a variety of different applicationsavailable on a variety of different operating systems. The search module312 may retrieve and analyze the application data from the applicationdata store 332 in order to perform application searches and to providesearch results 360.

In some implementations, the application data store 332 stores theapplication data in application records 340. Each application record 340can correspond to a third party application and may include theapplication data pertaining to the third party application. An exampleapplication record 340 includes an application name, an applicationidentifier, and other application features. The application record 340may generally represent the application data stored in the applicationdata store 332 that is related to the third party application.

The application name may be the name of the third party applicationrepresented by the data in the application record 340. Exampleapplication names may include “FACEBOOK®,” “TWITTER®,” “MICROSOFT®Word,” or “ANGRY BIRDS®.” The application identifier (hereinafter“application ID”) identifies the application record 340 amongst theother application records 340 included in the application data store332. In some implementations, the application ID may uniquely identifythe application record 340. The application ID may be a string ofalphabetic, numeric, and/or symbolic characters (e.g., punctuationmarks) that uniquely identify the third party application represented bythe application record 340. In some implementations, the application IDis the ID assigned to the application by a retail site (e.g., APP STORE®or GOOGLE PLAY®) that offers the application. In other implementations,the search server 300 assigns application IDs to each third partyapplication when creating an application record 340 for the third partyapplication.

The application features of a third party application may include anytype of data that may be associated with the third applicationrepresented by the application record 340. The application features mayinclude a variety of different types of metadata. For example, theapplication features may include structured, semi-structured, and/orunstructured data. The application features may include information thatis extracted or inferred from documents retrieved from other datasources (e.g., application retails sites, application developers, blogs,and reviews of applications) or that is manually generated (e.g.,entered by a human).

The application features may include the name of the developer of theapplication, a category (e.g., genre) of the application, a descriptionof the application (e.g., a description provided by the developer), aversion of the application, the operating system the application isconfigured for, and the price of the application. The applicationfeatures further include feedback units provided to the application.Feedback units can include ratings provided by reviewers of theapplication (e.g., four out of five stars) and/or textual reviews (e.g.,“This app is great”). The application features can also includeapplication statistics. Application statistics may refer to numericaldata related to the application. For example, application statistics mayinclude, but are not limited to, a number of downloads, a download rate(e.g., downloads per month), and/or a number of feedback units (e.g., anumber of ratings and/or a number of reviews). The application featuresmay also include information retrieved from websites, such as commentsassociated with the application, articles associated with theapplication (e.g., wiki articles), or other information. The applicationfeatures may also include digital media related to the application, suchas images (e.g., icons associated with the application and/orscreenshots of the application) or videos (e.g., a sample video of theapplication).

In some implementations, an application record 340 can group one or moreapplication editions under a canonical application structure. The termcanonical application structure can refer to a group of similarapplication editions. Put another way, the canonical applicationstructure may be a representative or umbrella under which the one ormore application editions are organized. Each application edition in agroup of application editions that are organized under the samecanonical application structure respectively indicates a version of athird party application that is functionally similar to other versionsof the third party application editions organized under the canonicalapplication structure. In other words, the application editions canrepresent different versions of the same third party application.Examples of edition applications are different release versions of anapplication (e.g., beta, 1.0, or 2.0), different language versions of anapplication (e.g., English, Russian, or Chinese), different platformversions of an application (e.g., iOS or ANDROID®), different functionalcharacteristics (e.g., a light version, an advanced user version),different aesthetic characteristics (e.g., a holiday themed version),and different resolution versions of an application (e.g., standarddefinition or high definition). Third party applications which arerelated but not similar (e.g., sequels in a series of games or adifferent release of a serial application) are typically not classifiedunder the same canonical application. For example, ANGRY BIRDS® may be aseparate canonical application from ANGRY BIRDS® STAR WARS®. Althoughthe applications may have a same underlying concept, they are treated asseparate games (i.e., third party applications).

The entity data store 334 may include one or more databases, indices(e.g., inverted indices), files, or other data structures. The entitydata store 334 stores one or more entity indexes 342. Each entity index342 indexes a plurality of entity records 344. Each entity record 344has an entity type. An entity type defines one of a plurality of variouscategories that are referenced in the entity data store 334.Non-limiting examples of entity types include “airport,” “movie,” “TVshow,” “actor,” “musician,” “band,” “song,” “album,” “restaurant,”“city,” “country,” ‘person,” “medicine,” “symptom,” and “time.” Eachentity record 344 represents a different entity. Each entity representsa species of a specific entity type. For example, the term “Toy Story”may be of the entity type “movie,” MCDONALDS® may be of the entity type“restaurant” and/or “fast food restaurant,” and “the Beatles” may be ofan entity type “band.” In some implementations, each entity type has acorresponding entity index 342. An entity data store 334 can be builtoff-line and/or can be continuously updated. In some examples, theentity index 342 is human curated, which may use existing data sources,such as FREEBASE® or WIKIPEDIA® to build the entity data store 334.Curators can define the entity types manually and the data sources maybe crawled to index all the various entities. Each entity type may havea particular record format corresponding thereto. For example, an entityrecord 344 for a restaurant entity may be: {entityTypeld:1,typeName:“Restaurant”, fields:[“name”, “foodType”]}. In this case,restaurant is an entity type name. The entity data store 334 may furtherinclude an application configuration database (not shown) that containsan application reference record for each entity-supporting application(e.g., third party applications). Each application reference recordincludes a name or application ID of a third party application and whichentity type or types that a particular third party application supports.For example, an application reference record corresponding to IMDB®(Internet Movie Database) may support movie entities, TV show entities,and actor entities. Similarly, an application reference record for theYELP® application may support restaurant entities, retail storeentities, or other establishment related entities.

The command template data store 336 stores a plurality of commandtemplates 346 for different third party applications. A command template346 may be a template defining a manner by which one or more stateparameters are accepted by a third party application. In someimplementations, the command templates 346 for a third party applicationinclude request command templates 346 c that are used to generaterequests that are sent to servers associated with third partyapplications. A request can refer to a communication that is provided toa resource (e.g., a web server 130 or application server 120) requestinga particular function. Additionally or alternatively, the commandtemplates 346 for a third party application can include commandtemplates 346 a, 346 b for generating resource identifiers 365. Thecommand templates 346 can be human curated or provided by the developerof the third party application. Furthermore, in some implementations,the command templates 346 implemented by a third party application canbe determined by parsing and analyzing the code of a third partyapplication (e.g., the HTML code of the web application) to identify theschema implemented by the third party application and the variousparameters that are accepted by the third party application.

According to some implementations, a web application command template346 a of a particular third party application is a template forgenerating a web resource identifier 365 a to access a particular stateor states of a web application (e.g., a URL). In some implementations, aweb resource identifier 365 a can indicate a domain name of a web server130 that executes a web application version of a third party applicationand one or more state parameters that define a state of the webapplication. For example, a web resource identifier 365 a may be auniform resource locator (URL), such that a first portion of the URL isthe domain name, and a second portion of the URL is a tail thatindicates a path defining one or more state parameters that can be usedto access a specified state of the web application. A web browser uses aweb resource identifier 365 a to access the state of the third partyapplication indicated therein by sending a web request to the web server130 referenced by the domain name, whereby the web request includes thestate parameters arranged in a manner defined in the web applicationcommand templates 346 a and/or schema. For example, a web requestcorresponding to the URL:“http://www.example.com/find?q=al+pacino&s=all” may be transmitted in anHTTP request to the server located at an address corresponding towww.example.com, and the state parameters can be included in the tailportion: “find?q=al+pacino&s=all.” In this example, the response to theweb resource identifier 365 a would include a web page that shows searchresults (360) resulting from the query terms “Al Pacino.” A webapplication command template 346 a can define a domain name of the webserver 130 of the web application (e.g., “www.domain.com”) and a paththat identifies parameter fields that receive parameters and the orderby which parameters are accepted by the webserver 130 (e.g.,“/<param_type_1>&<param_type_2″>, where param_type_1 and param_type_2are the types of parameters accepted by the web server 130 located athttp://www.domain.com). Each web application can have one or morecorresponding web command templates 346 a. In another example, a webapplication command template 346 a for a third party application maytake the form:

“http://www.domain.com/search?find_desc=<query_terms>&find_loc<loc>. Inthis example, the web command template 364 a includes two parameterfields: <query_terms>, which takes search query terms; and <loc> whichtakes in a location (e.g., city, state, and/or country).

According to some implementations, a native application command template346 b of a particular third party application is a template forgenerating an application resource identifier 365 b. An applicationresource identifier 365 b is a string of letters, numbers, and/orcharacters that corresponds to a state of a native application 218. Anative application 218 can parse an application resource identifier 365b to provide access to a state of the application. The applicationresource identifier 365 b identifies the native application 218. In somescenarios, the application resource identifier 365 b includes one ormore state parameters that correspond to the state of the application.The one or more state parameters can be used by the native application218 to access the state. An application resource identifier 365 b caninstruct the operating system 212 of a remote computing device 200 tolaunch a native application 218 based on a domain portion of theapplication resource identifier 365 b that references the nativeapplication 218 and to access a particular state of the nativeapplication 218 based on a tail portion that includes one or more stateparameters that define a state of the native application 218. When anapplication resource identifier 365 b is selected by a user of a remotecomputing device 200, the remote computing device 200 launches theapplication and accesses the state therein. A native application commandtemplate 346 b can include a domain portion that identifies the nativeapplication 218 (e.g., “example_app”) and a tail portion that identifiesparameter fields that receive parameters and the order by whichparameters are accepted by the native application 218 and/or anapplication server 120 (e.g., “::<param_type_1>: <param_type_2”>, whereparam_type_1 and param_type_2 are the types of parameters accepted bythe native application 218 “example_app”). Each native application 218can have one or more corresponding native application command templates346 b. In another example, a native application command template 346 bfor a third party native application may take the form:

“example_app::search?find_desc=<query_terms>&find_loc<loc>. In thisexample, the native application command template 346 b includes twoparameter fields: <query_terms>, which takes search query terms; and<loc> which takes in a location (e.g., city, state, and/or country).

The command template data store 336 may further store an associationtable for each third party application having command templates 346stored in the command template data store 336. An association table of athird party application can associate the different entity types thatare stored in the entity data store 334 with the parameter fields thatthe third party application accepts. For example, if a third partyapplication receives a location and a restaurant entities query in theform of <loc> and <rest_name>, respectively, the association table mayassociate location entities to <loc> and restaurant entities to<rest_name>.

In operation, the search module 312 receives query parameters 262, 264and identifies a set of third party applications corresponding to thequery parameters 262, 264. The search module 312 is configured toperform any type of suitable search. In some implementations, the searchmodule 312 can perform one or more of a functional search, an entitysearch, and a name search.

A functional search is a search for applications providing a particularfunctionality. Functional searching is different than name searching orkeyword searching in that functional searching usually aims to identifyapplications that provide a desired task, function, or feature (e.g.,find restaurant, take me to downtown, where to find the best burger)instead of specific keywords. For example, a functional search term maybe “make video calls to friends oversees,” compared to a name search of“SKYPE®.” In this example, the query does not include the term “SKYPE®,”and the description of the SKYPE® application does not mention the word“friends” or “overseas.” Therefore, traditional keyword searches mightnot identify the SKYPE® application as being relevant. As the SKYPE®application allows users to place video and voice calls across theworld, a functional search would likely identify the SKYPE® applicationin response to the “make video calls to friends overseas” queryparameter 262.

Functional searching may include searching for a third party applicationacross multiple platforms or constrained to certain platforms (e.g.,ANDROID® only). By way of example, in one embodiment a platform can be ahardware architecture and/or software framework, the combination ofwhich allows the software to run. Some examples of platforms include,but are not limited to, ANDROID®, BLACKBERRY® OS, MICROSOFT WINDOWS®Mobile, APPLE MAC OS®, APPLE iOS®. Functional searching can be supportedby the application data store 332. The application data store 332includes data from multiple third party sources such as, but not limitedto, blogs, application review sites, application catalogs, and/orapplication developers. Due to the different sources included in thefunctional database, functional searching leverages the multiple datasources and analyzes both the textual and non-textual features andprovides the user with a list of the best available applications basedon his/her inputted query terms. The application data store 332 mergesthe information that it gathers from the different sources and combinesthe information based on different version or editions of the sameapplication, providing a more comprehensive analysis. The applicationdata store 332 is indexed for faster retrieval of the data entries.

Operationally, the search module 312 can receive a query wrapper 260from a remote computing device 200. The search module 312 can processthe query parameters 262, 264 contained in the query wrapper 260. Thesearch module 312 may perform various processing operations on the queryparameters 262, 264. For example, analysis operations performed by thesearch module 312 may include, but are not limited to, tokenization ofthe query parameters 262, 264, filtering of the query parameters 262,264, stemming the search query 262, synonomyzation of the queryparameters 262, 264, and stop word removal. In some implementations, thesearch module 312 may further generate one or more subqueries based onthe query parameters 262, 264. Subqueries are search queries that arebased on some subcombination of the search query 262 and the other queryparameters 264.

The search module 312 identifies a consideration set of applications(e.g., a list of applications) based on the query parameters 262, 264and, in some implementations, the subqueries. In some examples, thesearch module 312 may identify the consideration set by identifyingapplications that correspond to the query parameters 262, 264 or thesubqueries based on matches between terms in the query parameters 262,264 (and/or the subqueries) and terms in the application data of theapplication (e.g., in the application record 262 of the application).For example, the search module 312 may identify one or more applicationsrepresented in the application data store 332 based on matches betweenterms or tokens representing the query parameters 262, 264 and terms ortokens included in the application records 340 of those applications.The consideration set may include a list of application IDs and/or alist of application names.

The search module 312 performs a variety of different processingoperations on the consideration set. In some implementations, the searchmodule 312 may generate a result score for each of the applicationsincluded in the consideration set. In some examples, the search module312 may cull the consideration set based on the result scores of theapplications contained therein. For example, the subset may be thoseapplications having the greatest result scores or have result scoresthat exceed a threshold. The result objects 362 included in the searchresults 360 may depend on how the search module 312 calculates theresult scores. For example, the result scores may depend on anycombination of the relevance of an application to the query parameters262, 264, the popularity of an application in the marketplace, theratings of an application, and other properties of the application.

The search module 312 may generate result scores for applications in avariety of different ways. In general, the search module 312 maygenerate a result score for an application based on one or more scoringfeatures. The scoring features may be associated with the applicationand/or the query parameters 262, 264. An application scoring feature mayinclude any data associated with an application. For example,application scoring features may include any of the application featuresincluded in the application record 340 or any additional featuresrelated to the application, such as data indicating the popularity of anapplication (e.g., number of downloads) and the ratings (e.g., number ofstars) associated with an application. A query scoring feature mayinclude any data associated with the query parameters 262, 264. Forexample, query scoring features may include, but are not limited to, anumber of terms in the search query 262, the popularity of the searchquery 262, and the expected frequency of the terms in the search query262. An application-query scoring feature may include any data, whichmay be generated based on data associated with both the application andthe query parameters 262, 264 (e.g., the query parameters 262, 264 thatresulted in identification of the application record 340 by the searchmodule 312). For example, application-query scoring features mayinclude, but are not limited to, parameters that indicate how well theterms of the query match the terms of the identified application record340. The search module 312 may generate a result score for anapplication based on at least one of the application scoring features,the query scoring features, and the application-query scoring features.

The search module 312 may determine a result score based on one or moreof the scoring features listed herein and/or additional scoring featuresnot explicitly listed. In some examples, the search module 312 mayinclude one or more machine learned models (e.g., a supervised learningmodel) configured to receive one or more scoring features. The one ormore machine learned models may generate result scores based on at leastone of the application scoring features, the query scoring features, andthe application-query scoring features. For example, the search module312 may pair the query parameters 262, 264 with each application andcalculate a vector of features for each (query, application) pair. Thevector of features may include application scoring features, queryscoring features, and application-query scoring features. The searchmodule 312 may then input the vector of features into a machine-learnedregression model to calculate a result score that may be used to rankthe applications in the consideration set. The search module 312 canthen rank the applications indicated in the consideration set based onthe result scores. Additionally or alternatively, the search module 312can cull the applications indicated in the consideration set based onthe result scores. The output of the functional search is a set of thirdparty applications based on the consideration set. The foregoing is anexample of how a result score is calculated. Some implementations maycalculate the result score in a different manner.

Additionally or alternatively, the search module 312 executes an entitysearch. An entity search is a search that attempts to identify the typesof entities referenced in a query, and in some cases, to identify thirdparty applications that are relevant to those entities. The searchmodule 312 can include the results of the entity search in the set ofthird party applications and/or can utilize the results to enhance theresults produced by the functional search. Entity searches are supportedby the entity data store 334.

In operation, the search module 312 receives the query parameters 262,264 and initiates an entity search. The search module 312 provides adatabase request to the entity data store 334 that includes one or moreof the terms of the query parameters 262, 264. When one or more termsare listed in the entity data store 334, the entity data store 334returns the entity types of the matched terms. The search module 312 canthen determine which third party applications are relevant to thereturned entity types based on the application reference records. Thesearch module 312 may be further configured to score each entitytype/third party application match by estimating a probability ofwhether the entity match is a good match. The search module 312 can useheuristic techniques to score the entity type/third party applicationmatch. The search module 312 can rank the matched applications based onthe calculated scores. The matched applications can be included in theset of third party applications. Additionally or alternatively, once thesearch module 312 has scored the applications, the results (e.g., listof applications and corresponding scores) of the entity search can beprovided as a signal to the functional search process. In theseimplementations, the functional search process can use the entity searchresults (360) as a signal for determining the results scores of theapplications in the consideration set.

In an example of an entity search, the query parameters 262, 264 maycontain the terms “Toy Story.” The search module 312 can identify “ToyStory” in the entity data store 334, which can be associated with one ormore entity types. For example, “Toy Story” may be identified as a movieentity. The search module 312 can then identify third party applicationsthat are related to movie entities. In this example, the search module312 can identify the IMDB® application, the NETFLIX® application, andthe ROTTEN TOMATOES® application as third party applications thatsupport movie entities. Thus, these third party applications may beindicated in the set of third party applications and/or may be used tocalculate the result scores of applications indicated in theconsideration set identified during the functional search process.

In some implementations, the search module 312 can store identifiedentities in the query parameters 262, 264 for later use. In theseimplementations, the stored entities can be used to send requests to aweb server 130 or application server 120 or to generate one or moreresource identifiers 365.

In some implementations, the search module 312 is further configured toperform name searches. A name search is a search for third partyapplications having a name that is explicitly included in the queryterms. The search module 312 can determine whether any of the terms inthe search query 262 match to a name of an application represented inthe application data store 332. If so, the search module 312 can includethe third party application defined by the application representation tothe set of third party applications. The foregoing search techniques areprovided for example only.

The forwarding module 314 is configured to forward one or more of thequery parameters 262, 264 to servers of the third party applicationsidentified by the search module 312. In some implementations, theforwarding module 314 determines a web server 130 and/or an applicationserver 120 associated with each third party application. In theseimplementations, the forwarding module 314 can obtain a request commandtemplate 346 c corresponding to the third party application fortransmitting a request to the web server 130 and/or the applicationserver 120. The forwarding module 314 can obtain the request commandtemplates 346 c of the third party application from the command templatedata store 336. Based on the request command template 346 c and the oneor more query parameters 262, 264, the forwarding module 314 formats anoutgoing request. The request command template 346 c can be based on theschema which is implemented by a particular third party application toreceive and process requests. Each third party application may acceptdifferent parameter types and different syntaxes for expressingparameters in requests that are provided to the third party application.Thus, a schema implemented by a third party application can define howit expects to receive requests, whereby each command template can bedefined to leverage a specific functionality of the third partyapplication.

The forwarding module 314 can generate an outgoing request by insertingone or more of the query parameters 262, 264 that were extracted fromthe query wrapper 260 into the command template 346 c. As discussed, thesearch module 312 can determine the entity type of at least a subset ofthe query parameters 262, 264. Furthermore, by identifying the commandtemplates 346 c of a particular third party application, the forwardingmodule 314 can understand the parameter types that are included in eachparticular command template 346 c of the third party application. Theforwarding module 314 can utilize an association table between entitytypes and parameter types to determine which query parameters to includein the outgoing request. For instance, a third party application formaking restaurant reservations may accept the following commandtemplate:

“http://www.ex_res_app.com/ex.aspx?d=<date>&t=<time>&r=<name>” and thequery may have included the following query terms: “French Laundry,” thecurrent date, and “9:00 P.M.” In this example, the search module 312determines that “French Laundry” is most likely a restaurant entity, thecurrent date is likely a date entity, and “9:00 P.M.” is most likely atime entity. Thus, the forwarding module 314 can generate the requestURL“http://www.ex_res_app.com/ex.aspx?d=<FEB28>&t=<2100>&r=<French_Laundry>”based on the command template 346 c referenced above. The forwardingmodule 314 can transmit the request to the web server 130 (orapplication server 120) corresponding to the third party application. Inthis way, the forwarding module 314 leverages the reservation makingfunctionality of the third party application. While a request URL isshown in the example above, the request may have any other suitableformat, such as an API call to the server of the third partyapplication.

The third party application processes the request, as it would any otherrequest from a remote computing device 200, and returns a responsecorresponding to the request. For example, if the third partyapplication is an online retailer that allows consumers to search forbrands or types of clothing, the third party application may return aresponse indicating items of clothing that are sold by a retailerassociated with the third party application, whereby the items indicatedin the response correspond to the parameters included in the request.

The response from the third party application may include a resourceidentifier 365. For example, a web server 130 may respond to a webrequest. The response may include the requested data and web resourceidentifier 365 a and/or an application resource identifier 365 b thatindicates where the requested data may be found. For example, if a thirdparty application is an application for making restaurant reservations,a server of the third party application may receive a request indicatinga restaurant name, a time, and a day. In response, the server 120, 130may return a response indicating whether making a reservation ispossible at the specified date and time and/or a resource identifier 365(e.g., web resource identifier 365 a or an application resourceidentifier 365 b) to a state of the third party application that allowsthe user to make the reservation.

The linking module 316 receives responses from the third partyapplications (i.e., from web servers 130 and/or application servers 120of the third party applications) and generates state links 364 to thethird party applications based on the responses received from eachrespective third party application. The linking module 316 includes thestate links 364 in the result objects 362 that are provided to theremote computing device 200 as part of the search results 360. In someimplementations, the linking module 316 receives web resourceidentifiers 365 a from web servers 130 associated with each of the thirdparty applications. For each web resource identifier 365 a, the linkingmodule 316 can generate a state link 364 that includes one or more webresource identifiers 365 a and/or one or more application resourceidentifiers 365 b. The linking module 316 can be configured to convert aweb resource identifier 365 a to an application resource identifier 365b. For example, the linking module 316 may utilize conversion rules forconverting from a web resource identifier 365 a to an applicationresource identifier 365 b. Conversion rules can be specific to specificthird party applications (e.g., a first conversion rule may apply to afirst third party application, while a second conversion rule can applyto a second third party application). A conversion rule can define howto convert a domain name in the web resource identifier 365 a to areference to a native application 218 that is included in theapplication resource identifier 365 b. A conversion rule can furtherdefine how to convert the state parameters appearing in the web resourceidentifier 365 a to the state parameters that are included in theapplication resource identifier 365 b.

Additionally or alternatively, the linking module 316 can generate statelinks 364 to particular states of third party applications using one ormore command templates corresponding to the third party applicationsindicated in the set of third party applications (identified by thesearch module 312), one or more of the terms contained in the queryparameters 262, 264, and in some cases, one or more entities and entitytypes identified by the search module 312. In some implementations, thelinking module 316 obtains the one or more command templates 346 fromthe command template data store 336 for each third party applicationindicated in the set of third party applications and, in some cases, theentity types determined by the search module 312. For example, for athird party application that allows a user to make restaurantreservations, the command templates 346 corresponding to the third partyapplication may include command templates 346 for generating webresource identifiers 365 a and application resource identifiers 365 b.Each command template 346 may indicate the types of parameters itreceives. Using an association table that associates entity types toparameter types accepted by the third party application, the linkingmodule 316 determines which entities can be entered in which parameterfields in each command template 346. The linking module 316 thensubstitutes the identified entities for the parameter fields in thecommand templates 346. In this way, for each third party applicationidentified in the set of third party applications, the linking module316 can generate one or more web resource identifiers 365 a and/orapplication resource identifiers 365 b that leverage one or morefunctionalities of the third party application without having to send arequest to a web server 130 or application server 120 of the third partyapplication.

The linking module 316, for each set of resource identifiers 365 thatcorrespond to a particular state, can imbed the set of resourceidentifiers 365 corresponding to a third party application in a statelink 364. In implementations where the state link 364 includes more thanone resource identifiers 365 (e.g., one or more application resourceidentifiers 365 b and a web resource identifier 365 a), the linkingmodule 316 can further include an instruction set with the state linkindicating an order to access the resource identifiers 365. Forinstance, the instruction set can instruct the remote computing device200 to first attempt to launch the native application 218 indicated byan application resource identifier 365 b and, if unsuccessful, to accessthe web application via the web browser of the remote user computingdevice 200. In some implementations, the instruction set is a script.

The viewing module 318 can determine a view of the state of the thirdparty application, which can be provided to the remote computing device200. A view of the state of a third party application can be, forexample, a graphical user interface (GUI) 250 of either a nativeapplication version or a web application version of the third partyapplication. In some implementations, the viewing module 318 can, forexample, access the web application at the determined state and capturea screen shot of the graphical user interface 250 of the web applicationat the state. In these implementations, the viewing module 318 canprovide the screen shot to the linking module 316, which provides thescreen shot with the state link. In some implementations, the screenshot is only taken of a portion of the screen that corresponds to thefunctionality implicated by the query.

In some implementations, the viewing module 318 is configured to providethe remote computing device 200 access to the actual third partyapplication (e.g., a native application version or a web applicationversion of the third party application). In these implementations, theviewing module 318 analyzes the code of a web application or a nativeapplication 218 to identify a particular segment of the code thatpertains to the desired function of a particular state of theapplication. The identified portion of the code can then be executedeither at the web server 130, the search server 300, or at the remotecomputing device 200, to provide the user with a functionality that isimplicated by the query. To support these implementations, the webapplication may be written in a programming language that segmentsbehaviors (e.g., specific functions) and presentation related to theassociated behavior in modular blocks. In this way, the viewing module318 can efficiently identify a modular block corresponding to a specificfunctionality or state, such that the viewing module 318 can provide theone or more query parameters 262, 264 to the modular block, which isexecuted using the one or more query parameters 262, 264. This allowsthe remote computing device 200 to receive a view of a particularfunction of the web application or native application 218 at the desiredstate, and further, to interact with the web or native application 218(e.g., provide additional input and/or receive additional output).

The results module 319 generates the search results 360 and provides thesearch results (360) to the remote computing device 200 that providedthe query. For each third party application in the set of third partyapplications, the results module 319 can generate a result object 362for the third party application. The result object 362 can include oneor more state links 364 to different states of the third partyapplication. As previously discussed, each state link 364 can include anapplication resource identifier 365 b and/or a web resource identifier365 a. Additionally or alternatively, the results module 319 can obtainvisual indicators 366 corresponding to the third party application andcan include the visual indicators 366 in the result object 362. Examplesof visual indicators 366 that can be included in a result object 362 ofa third party application include, an icon of the third partyapplication, a logo or image of an entity corresponding to the state ofthe third party application, and/or a screen shot of the third partyapplication. Additionally or alternatively, the results module 319 canobtain other data 368 corresponding to the third party application andcan include the other data 368 in the result object 362. Examples ofother data 368 corresponding to the third party application can includerankings, ratings, and/or descriptions corresponding to the third partyapplication and/or the entity corresponding to the state of the thirdparty application. The results module 319 can combine the result objects362 into the search results 360 and transmit the search results 360 tothe remote computing device 200.

FIG. 4A illustrates an example set of operations for a method 400 forproviding parameters to one or more third party applications. Forpurposes of explanation, the method 400 is described as being performedby the components of the search server 300.

At operation 410, the search module 312 receives a query (e.g., querywrapper 260) from the remote computing device 200. In someimplementations, the query may be provided from the remote computingdevice 200 via a partner device 140. As discussed, the query can includequery parameters 262, 264, including a search query 262 and otherparameters 264 such as the location of the remote computing device 200and/or an operating system 212 of the remote computing device 200. Thesearch module 312 parses the search query 262 to identify the queryterms. Further, the search module 312 can perform natural languageprocessing to extract features of the query terms. At operation 412, thesearch module 312 can identify a set of one or more third partyapplications which correspond to the query based on the query parameters262, 264 and/or the features of the query terms. As previouslydiscussed, the search module 312 can perform one or more of a functionalsearch, an entity search, and a name search to identify the set of thirdparty applications.

At operation 414, the forwarding module 314 transmits the queryparameters 262, 264 to servers associated with each of the third partyapplications indicated in the set of third party applications. FIG. 4Billustrates an example method 430 for transmitting the query parameters262, 264 to a server of a third party application. The method 430 can berepeated for each third party application indicated in the set of thirdparty applications.

At operation 440, the forwarding module 314 selects a command template346 corresponding to the third party application. The forwarding module314 can obtain one or more request command templates 346 c forgenerating requests from the command template data store 336, which canbe indexed by the third party application. As previously discussed, therequest command templates 346 c can be human curated, provided by theapplication developer of the third party application, or learned fromthe code of the third party application. The forwarding module 314 mayfurther be required to select a specific request command template 346 cwithin the third party application, such that the specific requestcommand template 346 c corresponds to the functionality implicated bythe query. For example, if a third party application allows a user torequest reviews of restaurants and to make restaurant reservations, thethird party application may be configured to receive at least requestscorresponding to two different request command templates 346 c. In somescenarios, the forwarding module 314 may select one or more of therequest command templates 346 c based on the entity types of the query.For example, if the query parameters 262, 264 include a restaurant name,a date, and a time, the forwarding module 314 may select a commandtemplate 346 for making reservations at a restaurant. Alternatively, theforwarding module 314 can select any command template 346 of the thirdparty application that defines parameter fields that correspond to theentity types implicated by the query parameters 262, 264.

At operation 442, the forwarding module 314 formats an outgoing requestbased on the command template 346 and the query parameters 262, 264. Theforwarding module 314 can insert the relevant query parameters 262, 264into the parameter fields defined in the command template 346 togenerate the outgoing request. The forwarding module 314 can utilizedefined associations between entity types and the parameter types of theparameter fields in the request command template 346 c to populate theparameter fields. For instance, if the entity type of a query termassociates to a parameter type, then the forwarding module 314 populatesthe parameter field with the query term.

At operation 444, the forwarding module 314 can transmit the outgoingrequest to a server, e.g., web server 130 or application server 120,associated with the third party application. The server associated withthe third party application processes the request and provides resultsto the search server 300.

The methods 400 and 430 of FIGS. 4A and 4B are provided for example andnot intended to limit the scope of the disclosure. Variations of themethods are contemplated and within the scope of the disclosure.

FIG. 5 illustrates an example set of operations for a method 500 forprocessing a query from a remote computing device 200. For purposes ofexplanation, the method 500 is described as being performed by thecomponents of the search server 300.

At operation 510, the search module 312 receives the query (e.g., querywrapper 260) from the remote computing device 200. For purposes ofexplanation only, the remote computing device 200 is explained as beinga remote computing device 200. In some implementations, the query may beprovided from the remote computing device 200 via a partner device 140.As discussed, the query can include query parameters 262, 264, includinga search query 262 and other parameters 264 such as the location of theremote computing device 200 and/or an operating system 212 of the remotecomputing device 200. The search module 312 parses the search query 262to identify the query terms of the search query 262. Further, the searchmodule 312 can perform natural language processing to extract featuresof the query terms.

At operation 512, the search module 312 can identify a set of one ormore third party applications which correspond to the query based on thequery parameters 262, 264 and/or the features of the query terms. Aspreviously discussed, the search module 312 can perform one or more of afunctional search, an entity search, and a name search to identify theset of third party applications.

At operation 514, the forwarding module 314 transmits one or more of thequery parameters 262, 264 to servers associated with each of the set ofthird party applications. In some implementations, the forwarding module314 can execute the method 430 described with respect to FIG. 4B whentransmitting the one or more query parameters 262, 264.

At operation 516, the linking module 316 receives a response from eachof the third party applications. The response may be received from, forexample, a web server 130 that executes a web application version of thethird party application. In this scenario, the response can include oneor more web resource identifiers 365 a, each of which identifying theweb server 130 and one or more state parameters that indicate a state ofa web application version of the third party application. For example,the response can include one or more URLs that each indicates a domainname of the web server 130 and one or more state parameters that can beused to access a particular state of the third party application. Inanother example, the response may be received from an application server120 that supports a native application version of the third partyapplication. In this scenario, the application server 120 can return oneor more application resource identifier 365 b, each identifying thenative application 218 and one or more state parameters that indicate astate of the native application version of the third party application.

At operation 518, the linking module 316 generates one or more statelinks 364 for each the third party application based on the respectiveresponses received from the servers of the third party applications. Asdiscussed above, the state link 364 can provide a mechanism to access astate of the native application version of the third party applicationand/or a state of the web application version of the third partyapplication. In implementations where the response is received from aweb server 130 of the third party application and includes a webresource identifier 365 a, the linking module 316 can convert the webresource identifier 365 a into one or more application resourceidentifiers 365 b based on one or more conversion rules. The linkingmodule 316 may convert the web resource identifier 365 a into multipleapplication resource identifiers 365 b when the third party applicationincludes more than one native application versions. In otherimplementations, the web server 130 or an application server 120associated with the third party application may provide one or moreapplication resource identifiers 365 b and one or more web resourceidentifiers 365 a in the response.

The linking module 316 embeds the one or more application resourceidentifiers 365 b in a state link 364. The linking module 316 mayfurther embed the web resource identifier 365 a in the state link 364and an instruction set for accessing the application. The instructionset can instruct the remote computing device 200 to attempt to accessthe native application 218 before using the web browsing application 216to access the web application. Additionally or alternatively, theinstruction set can instruct the remote computing device 200 to launch anative application 218 indicated in the state link 365 and can furtherinstruct the remote computing device 200 to input the state parametersinto a graphical user interface 250 of the native application 218.

At operation 520, the results module 319 transmits the state links 364for each of the third party applications to the remote computing device200. In some implementations, the results module 319 includes one ormore state links 364 in a result object 362 corresponding to the thirdparty application. The result processing module 319 can includeadditional data in each result object 362, such as one or more visualindicators 366 and/or other data 368. The result module 319 can includethe resource object 362 in the search results 360 and can transmit thesearch results 360 to the remote computing device 200.

The remote computing device 200 receives the state link 364 and canaccess the third party application by first attempting to launch thenative application 218 indicated by the state link 364. In doing so, theremote computing device 200 provides the one or more state parameters tothe native application 218, which may in turn provide the stateparameters to an application server 120. If unsuccessful in launchingthe native application 218, the remote computing device 200 can accessthe web application indicated by the web resource identifier 365 a inthe state link 364 using its web browser application 216.

While the discussion above states for “each third party application,”reference to “each third party application” does not necessarily requireall identified third party applications, but each third partyapplication that provides relevant responses. The method 500 of FIG. 5is provided for example and not intended to limit the scope of thedisclosure. Variations of the method are contemplated and within thescope of the disclosure. For example, the viewing module 318 can capturea screen shot of the application (web application or native application218) at the state indicated by the one or more state parameters. Thelinking module 316 can include the screen shot in the result object 362.

FIG. 6 illustrates an example set of operations for a method 600 forprocessing a query from a remote computing device 200. For purposes ofexplanation, the method 600 is described as being performed by thecomponents of the search server 300. According to the implementations ofFIG. 6, the search server 300 generates one or more resource identifiers365 to a third party application and a state link 364 containing theresource identifiers 365 without having to provide an outgoing requestto a server associated with the third party application.

At operation 610, the search module 312 receives a query from the remotecomputing device 200 containing query parameters 262, 264. At operation612, the search module 312 identifies a set of one or more third partyapplications that correspond to the query based on the query parameters262, 264. The search module 312 can perform one or more of a functionalsearch, an entity search, and a name search to identify the set of thirdparty applications.

At operation 614, the linking module 316 can determine one or morecommand templates 346 for each third party application in the set ofthird party applications. As was previously discussed, the commandtemplates 346 of a third party application can be obtained from thecommand template data store 336. The linking module 316 can obtain oneor more web application command templates 346 a and one or more nativeapplication command templates 346 b. In some implementations, thelinking module 316 can select the command templates 346 based on theentity types implicated by the query parameters 262, 264. In someimplementations, the linking module 316 uses an association tablecorresponding to the third party application to identify the entitytypes that may be accepted as parameters by the third party application(i.e., the parameter types accepted by the third party application).Based on the entity types implicated by the query parameters 262, 264and the parameter types accepted by the third party application, thelinking module 316 can select one or more command templates 346 from thecommand template data store 336. In this way, the linking module 316retrieves one or more command templates 346 that leverage a particularfunctionality of the third party application. For instance, the linkingmodule 346 can select one or more command templates 346 from a pluralityof command templates 346 corresponding to the third party applicationbased on the functionality that was implicated by the query parameters262, 264. In this example, the selected command templates 346 cancorrespond to different versions of the third party application (e.g., acommand template 346 b for iOS native application version, a commandtemplate 346 b for an ANDROID® native application version, and a commandtemplate 346 a for a web application version). Moreover, for each thirdparty application, the linking module 316 can select multiple commandtemplates 346 to leverage different functionalities of the third partyapplication.

At operation 616, the linking module 316 generates one or more resourceidentifiers 365 for each of the third party applications based on theretrieved command templates 346 and one or more of the query parameters262, 264. For each command template 346, the linking module 316 cansubstitute one or more of the query parameters 262, 264 that arerelevant to the command template 346 for the parameter fields defined inthe command template 346, as was described above. In some scenarios, thelinking module 316 can substitute identified entities in the queryparameters 262, 264, or the entire search query 262 itself for parameterfields defined in the respective command templates 346 a, 346 b. In thisway, the linking module 316 can generate one or more applicationresource identifiers 365 b and/or one or more web resource identifiers365 a corresponding to each third party application. In some scenarios,multiple application resource identifiers 365 b and/or multiple webresource identifiers 365 a can correspond to the same state of the thirdparty application. Put another way, the multiple resource identifiers365 may reference different versions of the third party application(e.g., IOS® version, ANDROID® version, free version, and/or payversion), but may all access the same state of the third partyapplication.

At operation 618, the linking module 316 can generate one or more statelinks 364 for each third party application. The linking module 316generates a state link 364 to the third party application based on thegenerated resource identifiers 365. The linking module 316 can insert anapplication resource identifier 365 b in a state link 364. The linkingmodule 316 may further include a web resource identifier 365 a in thestate link 364 and an instruction set for accessing the application(e.g., attempt to access the native application 218 before using the webbrowsing application 216 to access the web application).

At operation 620, for each of the third party applications, the linkingmodule 316 communicates the state link 364 to the remote computingdevice 200. In some implementations, the results module 319 includeseach state link 364 corresponding to a third party application in aresult object 362 corresponding to the third party application. Theresult processing module 319 can include additional data in each resultobject 362, such as one or more visual indicators 366 and/or other data368. The result processing module 319 can include the resource object362 for each third party application in the set of third partyapplications in the search results 360 and can transmit the searchresults 360 to the remote computing device 200.

While the discussion above states for “each third party application,”reference to “each third party application” does not necessarily requireall identified third party applications, but each third partyapplication that accepts a resource identifier 365 (web resourceidentifier 365 a and/or application resource identifier 365 b). Themethod 600 of FIG. 6 is provided for example and not intended to limitthe scope of the disclosure. Variations of the method 600 arecontemplated and within the scope of the disclosure.

FIGS. 7A-7B illustrate an example of a search that is performed on aremote computing device 200. In FIG. 7A, a user has entered a searchquery 262 into a GUI 250 on the search application 214. Specifically,the user has entered the search query 262 “Toy Story” into a search box252 of the GUI 250. In response to the search query 262, the searchapplication 214 generates a query wrapper 260 including the search query262 and any other parameters 264 and transmits the query wrapper 260 tothe search server 300. For example, the user can select (e.g., touch orclick) the search button 254 of the GUI 250 in order to initiatetransmission of the query wrapper 260 to the search server 300.

The search server 300 receives the query wrapper 260 and generatessearch results 360 based thereon. The search server 300 may transmitsearch results 360 including result objects 362 corresponding to a setof third party applications. In the illustrated example, the resultobjects 362 correspond to “IMDB®” (e.g., native and/or web application),“FANDANGO®” “CRACKLE®,” “FLIXSTER®,” and “ROTTEN TOMATOES®.” Each resultobject 362 may include one or more state links 364 corresponding to arelevant state of the application indicated in the search results 360. Auser may select (e.g., touch or click) one of the state links 364 toaccess the resource indicated in the state link 364. In response to sucha user selection, the search application 214 can instruct the operatingsystem 212 to launch the selected third party application and to accessthe state of the third party application indicated in the state link364.

In the example of FIG. 7A, the user selects the IMDB® state link 364 a.In the case of the IMDB® application, the various states of theapplication may correspond to different entries in the IMDB® databases.The illustrated IMDB® state link 364 a may include an applicationresource identifier 365 b that indicates a state corresponding to anentry for the movie “Toy Story.” Accordingly, selection of the IMDB®state link 364 a causes the search application 214 to instruct theoperating system 212 of the remote computing device 200 to launch theIMDB® native application 218 and to access the “Toy Story” entry on theIMDB® native application based on the application resource identifier365 b embedded in the state link 364 a. FIG. 7B illustrates a GUI 250 ofthe selected native application 218 that was launched in response to theselection of the IMDB® state link 364 a. In this example, the selectednative application displays an example entry for “Toy Story.”

FIGS. 8A-8B illustrate another example of a search that is performed ona remote computing device 200. In FIG. 8A, a user has entered a searchquery 262 into the GUI 250 of the search application 214. Specifically,the user has entered the search query “Late night diners by me” into asearch bar 252 of the GUI 250. In response to receiving the search query262, the search application 214 generates a query wrapper 260 includingthe search query 262 and other query parameters 264 (e.g., geo-locationof the device) and transmits the query wrapper 260 to the search server300.

The search server 300 receives the query wrapper 260 and generatessearch results 360 based thereon. The search server 300 may transmitsearch results 360 including a set of result objects 362 to the remotecomputing device 200. In the illustrated example, the result objects 362identify the “YELP®”, “OPENTABLE®,” “TRIPADVISOR®,” and “URBANSPOON®”applications. The GUI 250 may include state links 364 to theapplications in the search results 360. A user may select (e.g., touchor click) the state links 364 to access the resource indicated in thestate link 364. For example, a user may select the area of the GUI 250including the OPENTABLE® icon to select a state link 364 to theOPENTABLE® application. In another example, one or more state links 364may be provided for one or more applications listed in the search engineresult page.

The GUI 250 in FIG. 8A includes a plurality of different state links364. Three state links 364 a, 364 b, 364 c provide access to differentstates of the YELP® application. In the case of YELP®, each state maycorrespond to a different entry. For example, the state links 364 a, 364b, 364 c may provide access to entries for “IHOP®,” “DENNY'S®,” and“TACO BELL®,” respectively, in the YELP® application. In the example ofFIG. 8A, the user selects the DENNY'S® state link 364 b. The DENNY'S®state link 364 b may include an application resource identifier 365 b toan entry for the restaurant DENNY'S® in the YELP® native application.Accordingly, selecting the DENNY'S® state link 364 b causes the searchapplication 214 to instruct the operating system 212 to launch the YELP®native application and access an entry for DENNY'S® based on anapplication resource identifier embedded in the state link 364 a. FIG.8B shows an example GUI 250 of a selected application that the operatingsystem 212 launched in response to the selection of the DENNY'S® statelink 364 b.

FIGS. 9A and 9B illustrate another example of a search that may beperformed on a remote computing device 200. In FIG. 9A, a user hasentered the search query “thai” into the search bar 252 of the GUI 250and executed the search by, for example, selecting the search button 254of the GUI 250. In response to the search query 262, the searchapplication 214 generates a query wrapper 260 including the search query262 and any other query parameters 264 (e.g., geo-location and/oroperating system of the remote computing device 200) and transmits thequery wrapper 260 to the search server 300.

The search server 300 receives the query wrapper 260 and generatessearch results 360 based thereon. The search server 300 may transmitsearch results 360 including a set of result objects 362 to the remotecomputing device 200. The set of result objects 362 includes resultobjects 362 corresponding to the YELP® and OPENTABLE® applications. Eachresult object 362 include multiple state links 364 to the respectiveapplications. A user may select a state link 364 to access the entryindicated in the state link 364. For example, a user may select a statelink 364 a corresponding to the Bangkok Bistro to view the BangkokBistro entry in the YELP® application.

The GUI 250 in FIG. 9A includes three state links 364 a, 364 b, 364 cthat provide access to entries in the YELP® application. For example,the state links 364 a, 364 b, 364 c may provide access to entries for“Bangkok Bistro,” “Buda Thai,” and “Shang Thai Restaurant” in the YELP®application. The GUI in FIG. 9A includes three state links 364 d, 364 e,364 f that provide access to entries in the OPENTABLE® application. Forexample, the state links 364 d, 364 e, 364 f may provide access toentries for “Baan Thai House & Wine Bar,” “Basil Canteen @ 11th Street,”and “Blackwood” in the OPENTABLE® application. The state links 364 d,364 e, 364 f for “Baan Thai House & Wine Bar,” “Basil Canteen @ 11thStreet,” and “Blackwood,” respectively, include a portion of theOPENTABLE® application GUI 910 a, 910 b, 910 c relating to makingreservations at available reservation times. In this way, the user canaccess the functionality of the OPENTABLE® application directly from theGUI 250 of the search application 214.

The GUI 250 of FIG. 9A also includes icons 902 a, 902 b that indicatewhether the native applications for YELP® and OPENTABLE® are currentlyinstalled on the remote computing device 200. The “Open” icon 902 aindicates that the YELP® native application can be launched by theremote computing device 200, which implies that the YELP® nativeapplication is installed on the remote computing device 200. The usermay select (e.g., touch) the “Open” icon 902 a to launch the YELP®native application to a default state (e.g., a home screen” of the YELP®native application). The “Free” icon 902 b indicates that the OPENTABLE®native application can be downloaded to the remote computing device 200and is not installed thereon. In some examples, a user may select the“Free” icon 902 b to launch an application marketplace (e.g., GOOGLEPLAY® or the APP STORE®) that provides the OPENTABLE® native applicationfor download or to automatically start downloading the OPENTABLE® nativeapplication to the remote computing device 200. Selecting the Baan ThaiHouse & Wine Bar state link 364 d may cause the search application toattempt to launch the OPENTABLE® native application. When the remotecomputing device 200 determines that the attempt was unsuccessful, thesearch application 214 can instruct the operating system 212 to accessthe entry for Baan Thai House & Wine Bar in the OPENTABLE® webapplication based on the web resource identifier 365 a embedded in thestate link 364 d. FIG. 9B illustrates a GUI 250 of the OPENTABLE® webapplication that is displayed by the web browser of the remote computingdevice 200 in response to selection of the Baan Thai House & Wine Barstate link 364 d.

FIG. 10 illustrates another example of a search being performed on aremote computing device 200. In FIG. 10, the user has entered the searchquery “taxi” into the search bar 252 of the GUI 250. As described above,the search server 300 receives a query wrapper 260 containing the searchquery 262 and other query parameters 264 (e.g., geo-location of theremote computing device 200) from the remote computing device 200 andgenerates search results 360 based on the query wrapper 260. In theexample of FIG. 10, the search server 300 may forward a geo-locationquery parameter 264 to a server associated with the GETT® application ina request. In response, the server associated with the GETT® applicationmay return dynamic data, such as estimated distances of various taxidrivers with respect to the remote computing device 200 and an estimatedamount of time that that it would take for the taxi driver to arrive tothe user. The search server 300 can embed the dynamic data in the statelinks 364, such that the GUI 250 displays the dynamic data as additionaldata 368 in the state link 364. If the user wishes to make a taxireservation, the user can select one of the state links 364 to make thetaxi reservation. Selection of a state link 364 can launch the GETT®native application thereby initiating the taxi reservation.

The searches explained with respect to FIGS. 7A-10 are provided forexample only and are not intended to limit the types of searches thatmay be performed. Further, the results of the searches are provided forexample only and various search results 360 may be displayed in anyother suitable manner.

FIGS. 11A and 11B illustrate example operations performed by a searchserver 300 for processing a query received from a remote computingdevice 200. The operations 1100 described herein may be performed by theprocessing device 310 of the search server 300.

At operation 1110, the search server 300 receives a query from a remotecomputing device 200. In some implementations, the query is included ina query wrapper 260 that contains query parameters 264. The queryparameters 262, 264 can include a search query 262 (i.e., one or morequery terms). In some implementations, the query parameters 262, 264 canfurther include additional query parameters 264 (e.g., a geo-location ofthe remote computing device 200, an operating system 212 of the remotecomputing device 200, a device type of the remote computing device 200,and/or a username of the user of the remote computing device 200).

At operation 1112, the search server 300 identifies a set of third partyapplications corresponding to the query. The search server 300 canperform one or more of a functional search, an entity search, or a namesearch using the query parameters 262, 264 received in the query wrapper260. The result of the search or searches is a set of third partyapplications that are relevant to one or more of the query parameters262, 264 provided in the query wrapper by the remote computing device200.

At operation 1114, the search server 300 generates one or more resourceidentifiers 365 for the third party applications indicated in the set ofthird party applications. For a third party application, the searchserver 300 generates resource identifiers 365 based on the queryparameters 262, 264 and the command templates 346 corresponding to thethird party application. The search server 300 can identify relevantcommand templates 346 from the command template data store 336 based onentity types of one or more of the query parameters 262, 264. Forexample, if the query parameters 262, 264 include a movie name and atime and the set of applications include an application for findingmovie times at movie theatres near the remote computing device 200, thesearch server 300 may identify one or more command templates 346 thatreceive these types of parameters. The search server 300 may utilize anassociation table corresponding to the third party application toidentify the relevant parameters that were included in the queryparameters 262, 264. The search server 300 can identify web applicationcommand templates 346 a and/or native application command templates 346b for the third party application. The search server 300 can substitutethe relevant query parameters 262, 264 into the parameters fieldsdefined in the command templates 346, each time generating a resourceidentifier 365.

At operation 1116, the search server 300 generates one or more statelinks 364 for the third party applications based on the generatedresource identifiers 365. The search server 300 can embed the generatedapplication resource identifiers 365 b and/or web resource identifiers365 a into a state link 364. In some scenarios, the search server 300can select more than one resource identifier 365 to embed in a statelink 364. For example, if the third party application accepts bothapplication resource identifiers 365 b (for launching a nativeapplication 218 of the third party application to a specified state) andweb resource identifiers 365 a (for accessing a web application of thethird party application at a specified state), then the search server300 can select multiple resource identifiers 365 for inclusion in thestate link 364, provided the resource identifiers 365 correspond to thesame state (e.g., provide the same information). When the state link 364contains more than one resource identifier, the search server 300 canfurther include a set of instructions indicating an order by which theresource identifiers can be selected. For example, the set ofinstructions can instruct the remote computing device 200 to attempt tolaunch the native application 218 using the application resourcecontained in the state link 364, and if unsuccessful, to access the webapplication using the web resource identifier 365 a contained in thestate link 364. In some implementations, the search server 300 includesadditional data in the state link 364. For example, the search server300 can include visual indicators 366 (e.g., icons, logos, screen shots,GUI 250 elements of the third party application) and/or metadata (e.g.,descriptions, ratings, rankings, and dynamic data) in the state link364. The additional data can be obtained from any suitable source,including a server associated with the third party application, theapplication data store 332, and/or the entity data store 334.

At operation 1118, the search server 300 generates search results 360based on the generated state links 364. For each third party applicationin the set of third party applications, the search server 300 can groupthe state links 364 for the third party application together. The searchserver 300 can then generate a result object 362 for the third partyapplication based on the grouped state links 364. The search results 360include the result objects 362 corresponding to each of the third partyapplications.

At operation 1120, the search server 300 transmits the search results360 to the remote computing device 200. The remote computing device 200can then display the search results 360 via its user interface device240. The user can access a state of a third party application indicatedin the search results (360) by selecting a state link 364 included inthe search results 360.

FIGS. 12A and 12B illustrate example operations 1200 performed by asearch server 300 processing a query received from a remote computingdevice 200. The operations 1200 described herein may be performed by theprocessing device 310 of the search server 300.

At operation 1210, the search server 300 receives a query from a remotecomputing device 200. In some implementations, the query is included ina query wrapper 260 that contains query parameters 262, 264. The queryparameters 262, 264 can include a search query 262 (i.e., one or morequery terms). In some implementations, the query parameters 262, 264 canfurther include additional query parameters 264 (e.g., a geo-location ofthe remote computing device 200, an operating system of the remotecomputing device 200, a device type of the remote computing device 200,and/or a username of the user of the remote computing device 200).

At operation 1212, the search server 300 identifies a set of third partyapplications corresponding to the query. The search server 300 canperform one or more of a functional search, an entity search, or a namesearch using the query parameters 262, 264 received in the query. Theresult of the search or searches is a set of third party applicationsthat are relevant to one or more of the query parameters 262, 264provided in the query by the remote computing device 200.

At operation 1214, the search server 300 generates requests based onrequest command templates 346 c corresponding to the third partyapplications. For each relevant third party application, the searchserver 300 retrieves one or more request command templates 346 c fromthe command template data store 336. The search server 300 can determinewhich request command templates 346 c to retrieve based on the entitytypes contained in the query. In some implementations, the search server300 utilizes an association table to identify relevant request commandtemplates 346 c. The search server 300 can insert identified entitiesfrom the query into the parameter fields of a request command template346 c to generate a request.

At operation 1216, the search server 300 transmits the requests to theservers of the third party applications indicated in the set of thirdparty applications. In some implementations, the requests for aparticular third party application can be sent to a web server 130 ofthe third party application. At operation 1218, the search server 300receives responses from the servers of the third party applications. Inimplementations where the server is a web server 130, the response caninclude a web resource identifier 365 a of a state corresponding to theparameters included in the request. The search server 300 may receivemultiple responses from multiple servers.

At operation 1220, the search server 300 generates state links 364 basedon the responses. In some implementations, the search server 300 canconvert the web resource identifiers 365 a received in the responsesinto application resource identifiers 365 b based on conversion rulescorresponding to each respective third party application. In somescenarios, a conversion rule can result in multiple application resourceidentifiers 365 b being converted from a web resource identifier 365 a(e.g., in the case of multiple versions of the native application 218).The search server 300 can group application resource identifiers 365 band a web resource identifier 365 a corresponding to the same state ofthe third party application together. The search server 300 can embedthe grouped application resource identifiers 365 b and web resourceidentifier 365 a into a state link 364. In this way, the search server300 can generate multiple state links 364 for a third party application,and can generate one or more state links 364 for each of the third partyapplications indicated in the set of third party applications. When thestate link 364 contains more than one resource identifier 365 (e.g., oneor more application resource identifiers 365 b and a web resourceidentifier 365 a), the search server 300 can further include a set ofinstructions indicating an order by which the resource identifiers 365can be selected. For example, the set of instructions can instruct theremote computing device 200 to attempt to launch the native application218 using the application resource application identifier 365 bcontained in the state link 364 and if unsuccessful to access the webapplication using the web resource identifier 365 a contained in thestate link 364. In some implementations, the search server 300 includesadditional data in the state link 364. For example, the search server300 can include visual indicators 366 (e.g., icons, logos, screen shots,GUI 250 elements of the third party application) and/or metadata (e.g.,descriptions, ratings, rankings, dynamic data) in the state link 364.The additional data can be obtained from any suitable source, includinga server associated with the third party application, the applicationdata store 332, and/or the entity data store 334.

At operation 1222, the search server 300 generates search results 360based on the state links 364. For each third party application having atleast one state link 364 generated therefor, the search server 300 cangroup the state links 364 for the third party application together. Thesearch server 300 can then generate a result object 362 for the thirdparty application based on the grouped state links 364. The searchresults 360 include the result objects 362 corresponding to each of thethird party applications.

At operation 1224, the search server 300 transmits the search results360 to the remote computing device 200. The remote computing device 200can then display the search results 360 via its user interface device240. The user can access a state of a third party application indicatedin the search results 360 by selecting a state link 364 included in thesearch results 360.

Computing Machine Architecture

FIG. 13 is a block diagram illustrating components of an example machineable to read instructions from, for example, a non-transitorymachine-readable medium and execute them in one or more processors (orcontrollers). Specifically, FIG. 13 shows a diagrammatic representationof a machine in the example form of a computer system 1300 within whichinstructions 1324 (e.g., software or program code) for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed. The methodologies include those described with respectto FIGS. 3A, 3B, 4, 5, and 6. In alternative embodiments, the machineoperates as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine may operate inthe capacity of a server machine or a client machine in a server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment.

The machine for this configuration may be a mobile computing device suchas a tablet computer, an ultrabook (or netbook) computer, a personaldigital assistant (PDA), a cellular telephone, a smartphone, a webappliance, or like machine capable of executing instructions 1324(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines thatindividually or jointly execute instructions 1324 to perform any one ormore of the methodologies discussed herein.

The example computer system 1300 includes one or more processors 1302(e.g., a central processing unit (CPU) and may also include a graphicsprocessing unit (GPU), a digital signal processor (DSP), one or moreapplication specific integrated circuits (ASICs), one or moreradio-frequency integrated circuits (or chipset) (RFICs), a wirelessfidelity (WiFi) chipset, a global positioning system (GPS) chipset, anaccelerometer (one, two, or three-dimensional), or any combination ofthese). The computer system 1300 also includes a main memory 1304 and astatic memory 1306. The components of the computing system areconfigured to communicate with each other via a bus 1308. The computersystem 1300 may further include a graphics display unit 1310 (e.g., aplasma display panel (PDP), a liquid crystal display (LCD), glassdisplay) which may be configured for capacitive or inductive touchsensitivity to allow for direct interaction with software userinterfaces through the display 1310. The computer system 1300 may alsoinclude an alphanumeric input device 1312 (e.g., a keyboard), a cursorcontrol device 1314 (e.g., a mouse, a trackball, a joystick, a motionsensor, or other pointing instrument), a storage unit 1316, a signalgeneration device 1318 (e.g., a speaker), and a network interface device1320, which also are configured to communicate via the bus 1308.

The storage unit 1316 includes a machine-readable medium 1322 on whichis stored instructions 1324 (e.g., software) embodying any one or moreof the methodologies or functions described herein. The instructions1324 (e.g., software) may also reside, completely or at least partially,within the main memory 1304 or within the processor 1302 (e.g., within aprocessor's cache memory) during execution thereof by the computersystem 1300, the main memory 1304 and the processor 1302 alsoconstituting machine-readable media. The instructions 1324 (e.g.,software) may be transmitted or received over a network 1326 via thenetwork interface device 1320.

While machine-readable medium 1322 is shown in an example embodiment tobe a single medium, the term “machine-readable medium” should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions (e.g., instructions 1324). The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring instructions (e.g., instructions 1324) for execution by themachine and that cause the machine to perform any one or more of themethodologies disclosed herein. The term “machine-readable medium”includes, but may not be limited to, data repositories in the form ofsolid-state memories, optical media, and magnetic media.

Additional Configuration Considerations

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Various implementations of the systems and methods described here can berealized in digital electronic and/or optical circuitry, integratedcircuitry, specially designed ASICs (application specific integratedcircuits), computer hardware, firmware, software, and/or combinationsthereof. These various implementations can include implementation in oneor more computer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications, scripts, or program code) include machine instructions,e.g., 1324, for a programmable processor, e.g., 1302, and can beimplemented in a high-level procedural and/or object-orientedprogramming language, and/or in assembly/machine language. The computerprograms can be structured functionality in units referenced as“modules,” for example, as illustrated in FIG. 2. As used herein, theterms “machine-readable medium” and “computer-readable medium” refer toany computer program product, non-transitory computer readable medium,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

Implementations of the subject matter and the functional operationsdescribed in this specification can be implemented in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Moreover,subject matter described in this specification can be implemented as oneor more computer program products, i.e., one or more modules of computerprogram instructions encoded on a computer readable medium for executionby, or to control the operation of, data processing apparatus. Thecomputer readable medium can be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more of them. The terms data processing apparatus“, “computingdevice” and “computing processor” encompass all apparatus, devices, andmachines for processing data, including by way of example a programmableprocessor, a computer, or multiple processors or computers. Theapparatus can include, in addition to hardware, code that creates anexecution environment for the computer program in question, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them. A propagated signal is an artificially generated signal, e.g.,a machine-generated electrical, optical, or electromagnetic signal thatis generated to encode information for transmission to suitable receiverapparatus.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program does not necessarily correspond to a file in a filesystem. A program can be stored in a portion of a file that holds otherprograms or data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto optical disks, or optical disks. However, a computerneed not have such devices. Moreover, a computer can be embedded inanother device, e.g., a mobile telephone, a personal digital assistant(PDA), a mobile audio player, a Global Positioning System (GPS)receiver, to name just a few. Computer readable media suitable forstoring computer program instructions and data include all forms ofnon-volatile memory, media and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, one or more aspects of thedisclosure can be implemented on a computer having a display device,e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, ortouch screen for displaying information to the user and optionally akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

One or more aspects of the disclosure can be implemented in a computingsystem that includes a backend component, e.g., as a data server, orthat includes a middleware component, e.g., an application server, orthat includes a frontend component, e.g., a client computer having agraphical user interface or a Web browser through which a user caninteract with an implementation of the subject matter described in thisspecification, or any combination of one or more such backend,middleware, or frontend components. The components of the system can beinterconnected by any form or medium of digital data communication,e.g., a communication network. Examples of communication networksinclude a local area network (“LAN”) and a wide area network (“WAN”), aninter-network (e.g., the Internet), and peer-to-peer networks (e.g., adhoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someimplementations, a server transmits data (e.g., an HTML page) to aclient device (e.g., for purposes of displaying data to and receivinguser input from a user interacting with the client device). Datagenerated at the client device (e.g., a result of the user interaction)can be received from the client device at the server.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular implementations of the disclosure. Certain features that aredescribed in this specification in the context of separateimplementations can also be implemented in combination in a singleimplementation. Conversely, various features that are described in thecontext of a single implementation can also be implemented in multipleimplementations separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multi-tasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. Accordingly, otherimplementations are within the scope of the following claims. Forexample, the actions recited in the claims can be performed in adifferent order and still achieve desirable results.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and a process for deep search in computing environments throughthe disclosed principles herein. Thus, while particular embodiments andapplications have been illustrated and described, it is to be understoodthat the disclosed embodiments are not limited to the preciseconstruction and components disclosed herein. Various modifications,changes and variations, which will be apparent to those skilled in theart, may be made in the arrangement, operation and details of the methodand apparatus disclosed herein without departing from the spirit andscope defined in the appended claims.

What is claimed is:
 1. A method comprising: at a mobile computing deviceincluding a touchscreen display, a transceiver, a non-transitory memory,and one or more processors: displaying a first graphical user interface(GUI) via a first native application that is installed at the mobilecomputing device, wherein the first GUI is configured to accept searchqueries; receiving a search query via the first GUI, wherein the searchquery comprises one or more search terms; transmitting, via thetransceiver, the search query to a search engine operated by a searchengine operator; receiving, via the transceiver, search results inresponse to transmitting the search query, wherein at least one of thesearch results includes a post execution view of a second nativeapplication; and displaying the post execution view on the touchscreendisplay, wherein the post execution view comprises a second GUI thatprovides direct access to a function associated with the second nativeapplication; and at the search engine including a network interfacedevice, a non-transitory memory and one or more processors: receivingthe search query from the mobile computing device via the networkinterface device; identifying, based on the search terms of the searchquery, a set of third party applications, including the second nativeapplication, corresponding to the search query specified in an indexthat stores information related to the set of third party applications,each third party application of the set of third party applicationscomprising code that is executable at the mobile computing device; foreach third party application of the set of third party applications,transmitting a query parameters to a server associated with the set ofthird party applications, for each third party application of the set ofthird party applications, receiving a response from the serverassociated with the set of third party application, executing the codeassociated with each third party application of the set of third partyapplications upon receiving the response from the server associated withthe set of third party application; generating the post execution viewof a particular state of each third party application upon executing thecode; and transmitting the post execution view of the particular stateof each third party application of the set of third party applicationsto the mobile computing device as a search result.
 2. The method ofclaim 1, wherein the second GUI is configured to accept a user input. 3.The method of claim 2, wherein the second GUI comprises a search fieldthat is configured to receive the user input.
 4. The method of claim 1,wherein the second GUI is configured to display information associatedwith the second native application.
 5. The method of claim 4, whereinthe search terms indicate a location; and wherein the second GUIdisplays information that is associated with the location.
 6. The methodof claim 1, wherein: the second native application comprises anapplication for making reservations; and the second GUI enables a userof the mobile computing device to make a reservation.
 7. The method ofclaim 6, wherein: the search terms specify a location; and the secondGUI enables the user of the mobile computing device to make thereservation at or near the location.
 8. The method of claim 1, wherein:the search results comprise a user-selectable link; and displaying thepost execution view comprises: detecting a user selection of theuser-selectable link; and displaying the post execution view in responseto detecting the user selection of the user-selectable link.
 9. Themethod of claim 1, wherein generating the post execution view comprisesdetermining a screen of the second native application.
 10. The method ofclaim 1, wherein identifying the set of third party applicationscomprises searching the index that stores information related to the setof third party application for third party applications that arerelevant to the search query.
 11. The method of claim 1, wherein thesecond GUI comprises GUI elements that accept data.
 12. The method ofclaim 11, further comprising: at the search engine: populating at leastone of the GUI elements that accept data with one or more of the searchterms.
 13. The method of claim 1, further comprising: at the searchengine: indexing content associated with the set of third partyapplications into the index.
 14. The method of claim 1, wherein: thesearch results comprise a link to download the second nativeapplication; and the method further comprises: at the mobile computingdevice: displaying the link to download the second native application.15. The method of claim 14, further comprising: at the mobile computingdevice: detecting a user selection of the link; and downloading thesecond native application upon detecting the user selection of the link.16. The method of claim 15, wherein downloading the second nativeapplication comprises: launching an application marketplace that enablesa user of the mobile computing device to download the second nativeapplication.
 17. The method of claim 1, wherein displaying the first GUIcomprises displaying a search box.
 18. The method of claim 17, whereindisplaying the search box comprises displaying the search box on a homescreen.
 19. The method of claim 1, wherein receiving the search querycomprises receiving text via the first GUI.
 20. The method of claim 1,wherein receiving the search query comprises detecting speech via thefirst GUI.
 21. The method of claim 1, wherein the first nativeapplication comprises a search application developed by the searchengine operator.